Service Availability

The Service Availability option is used for monitoring the availability of service for SBC devices that are deployed in the Live Platform topology. Devices can be grouped into clusters representing deployed service topologies. Live Platform monitors the SBC devices in the cluster, calculating their availability based on connection time calculated over a three-hour sampling interval. Live Platform samples the devices that are attached to the cluster every five minutes. If connection cannot be established by Live Platform to all of the devices configured in the cluster, then Downtime is calculated as a ratio of the total number of minutes during the three-hour interval when connection cannot be established to all devices in the cluster. For example, if there are two devices in the cluster, where both report 36 minutes of downtime, then the calculation is 36/180=0.2 (20% downtime), therefore the availability percentage is 80%.

If downtime is experienced during the entire duration of this period, then this value is 180. Availability reports can be generated and exported as .CSV files (see Export Availability Data).

You can initially configure the committed availability percentage value for the cluster according to the service agreement and then monitor the deviation from this value. For example if the Availability percentage is set to 90% and the reported data is calculated as 80%, then this differential may be taken into account for service billing.

These reports are used for Service-level and Customer-level Availability reporting. For Service level, separate clusters can be defined for example, for Direct Routing and Operator Connect. Disruptions to Service Availability can then be correlated to specific actions performed on the SBC device. For example, when uploading numbers to the Operator Connect service, numbers are uploaded simultaneously to multiple SBC devices, to the Microsoft platform and to the Live Platform UMP-365 device. Users can then correlate the downtime for SBC devices to validate connection issues when partial number upload responses are received on the Live Platform.

➢

Do the following:

1.

In the Menu bar, choose Topology and then select the Service Availability tab.

The table below describes the parameters in this page.

Parameter	Description
Name	Name of the cluster.
Description	Brief description of the cluster.
Committed Availability	The percentage utilization of the cluster resources. For example 90.0 indicates that 90 % of the cluster resources are utilized. This value is between 1-100.
Availability Percentage	The available percentage of resources in the cluster (e.g., 99.90%) based on the ratio of downtime to total time (minutes of unavailability divided by 180 minutes). This percentage reflects the time that all devices in the cluster are simultaneously down. For example, if NY-SBC , WS-SBC and NJ-SBC are simultaneously down for 30 minutes, then the calculated percentage is 30/180=0.16 (16% downtime), therefore the availability percentage is 100-16=84%. When the SBC device is moved between clusters historical sampled data from the original cluster affects the Availability calculation in the new cluster. You can then filter data for the time period that you wish to analyze.
Number of Devices	The number of devices in the cluster. Maximum devices in one cluster is 10. Default value 3
Total Raw Downtime	The historical sampled downtime (minutes) over a three hour interval period that all devices in the cluster are not connected to Live Platform. If the devices are not connected for the entire duration of the interval then the value is 180 minutes.
Total Calculated Downtime	The downtime calculated accounting for Justifications that are external mitigating factors to the operation of the device. For example, a power outage. In this case, the Total Raw Downtime value is reset to 0 as a result of the configured Justification (see example above).